Skip to content

Conversation

@SunDevil311
Copy link
Member

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Changed

  • Bumped version to v1.18.0
  • Migrated hosting and serverless functions from Netlify to Vercel.
  • Updated deployment configuration to use @sveltejs/adapter-vercel in place of
    @sveltejs/adapter-netlify.
  • Cleaned up Netlify-specific files and settings:
    • Removed netlify.toml and Netlify plugin configuration.
    • Removed unused SMTP-related environment variables (SMTP_*, MAIL_ENABLED,
      NOTIFY_EMAIL).
    • Replaced _redirects with Vercel-managed redirects and rewrites in
      vercel.json.
  • Updated environment configuration to define ENV_MODE within Vercel project
    settings.
  • Adjusted engines.npm requirement in package.json from >=11.0.0 <12 to >=10.0.0 <12 for compatibility with Vercel.

Removed

  • Deleted netlify.toml and _redirects.
  • Removed vercel.json from .gitignore.

Checklist

  • I have read and followed the guidelines in the CONTRIBUTING document.
  • I've checked for existing Pull Requests for the same update/change.
  • My code follows the project’s coding style.
  • My code has been linted locally before submission.
  • All new and existing tests pass.

 

  • I have updated the documentation accordingly.
  • I have added tests to cover my changes, if applicable. (Optional, especially for new contributors)

Pull requests are part of a collaborative process — we welcome contributions and review each one carefully. For all but the smallest changes, you can expect maintainers to request improvements or clarifications.

Please check back after opening your PR and be responsive to feedback so we can get your contribution merged quickly.

Thanks for helping improve Network Pro Strategies!

@vercel
Copy link

vercel bot commented Sep 28, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
web Ready Ready Preview Comment Sep 28, 2025 1:17am

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.74)
  • Largest Contentful Paint (score: 0.16)
  • Speed Index (score: 0.98)
  • Time to Interactive (score: 0.67)
  • Avoid multiple page redirects (score: 0)
  • Largest Contentful Paint element (score: 0)
  • Links rely on color to be distinguishable. (score: 0)
  • Serve static assets with an efficient cache policy (score: 0.5)
  • Reduce unused JavaScript (score: 0)
  • Avoid serving legacy JavaScript to modern browsers (score: 0)
  • Use efficient cache lifetimes (score: 0.5)
  • Legacy JavaScript (score: 0.5)
  • Network dependency tree (score: 0)
  • Render blocking requests (score: 0.5)

View the full report in the workflow artifacts or in .lighthouseci/report.html.

Copy link
Member Author

@SunDevil311 SunDevil311 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All changes look good. Netlify failure is expected. Merging.

@SunDevil311 SunDevil311 merged commit 8716f12 into master Sep 28, 2025
10 of 14 checks passed
@SunDevil311 SunDevil311 deleted the feature/vercel-migration branch September 28, 2025 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants